Enablement of licensed features at a logical volume level of granularity

ABSTRACT

A licensing application implemented in a computational device receives a request to enable a feature for a logical volume of a plurality of logical volumes controlled by the computational device, wherein each feature of a plurality of features is configurable to be enabled or disabled for one or more logical volumes of the plurality of logical volumes. The licensing application determines, whether enabling the feature for the logical volume causes a licensed capacity limit for the feature to be exceeded. Enabling the feature for the logical volume is avoided, in response to determining that enabling the feature for the logical volume causes the licensed capacity limit for the feature to be exceeded.

BACKGROUND

1. Field

The disclosure relates to a method, a system, and a computer programproduct for the enablement of licensed features at a logical volumelevel of granularity.

2. Background

A hardware or software product may include a plurality of features,wherein a feature may correspond to a function that is capable of beingperformed by the product. The product may be configurable in a mannersuch that selected features may be enabled or disabled in the productvia a licensing mechanism. In such situations, the selected featuresthat are enabled may be referred to as licensed features. For example,certain software vendors may provide a free version of a software inwhich only a restricted set of features are enabled, and on receipt of alicensing fee may enable additional features that are not available foruse in the free version.

Certain mechanisms may provide a licensing key to a customer who ordereda feature for a product. The licensing key may be an encoded value thatmay be decoded by a program and verified, and based on verification ofthe licensing key the ordered feature may be enabled in the product. Incertain situations, licensing mechanisms may be used in environments inwhich a plurality of storage devices are controlled by a storagecontroller.

SUMMARY OF THE PREFERRED EMBODIMENTS

Provided are a method, a system, and a computer program product, inwhich a licensing application implemented in a computational devicereceives a request to enable a feature for a logical volume of aplurality of logical volumes controlled by the computational device,wherein each feature of a plurality of features is configurable to beenabled or disabled for one or more logical volumes of the plurality oflogical volumes. The licensing application determines, whether enablingthe feature for the logical volume causes a licensed capacity limit forthe feature to be exceeded. Enabling the feature for the logical volumeis avoided, in response to determining that enabling the feature for thelogical volume causes the licensed capacity limit for the feature to beexceeded.

In further embodiments, the feature is enabled for the logical volume,in response to determining that enabling the feature for the logicalvolume does not cause the licensed capacity limit for the feature to beexceeded.

In yet further embodiments, the computational device is a storagecontroller, wherein the plurality of logical volumes are generated fromphysical volumes of a plurality of storage devices coupled to thestorage controller. In response to an enablement or disablement of oneor more selected features for one or more logical volumes of a group ofsequentially numbered logical volumes, a single interrupt is sent fromthe storage controller to each host of a plurality of hosts that arecoupled to the storage controller, wherein the single interrupt isindicative of changes in the one or more selected features for alllogical volumes of the group of sequentially numbered logical volumes.

In additional embodiments, selected logical volumes of the plurality oflogical volumes are grouped into a resource group. In response to arequest for enablement of a selected feature for the resource group, adetermination is made as to whether enabling the selected feature forall the selected logical volumes of the resource group causes a licensedcapacity limit for the selected feature to be exceeded. Enabling theselected feature for the resource group is avoided, in response todetermining that enabling the selected feature for all the selectedlogical volumes of the resource group causes the licensed capacity limitfor the selected feature to be exceeded, wherein enabling the selectedfeature for the resource group causes the selected feature to be enabledfor all the selected logical volumes of the resource group.

In yet additional embodiments, the selected feature is enabled for theresource group, in response to determining that enabling the selectedfeature for all the selected logical volumes of the resource group doesnot cause the licensed capacity limit for the selected feature to beexceeded.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers representcorresponding parts throughout:

FIG. 1 illustrates a block diagram of a computing environment thatincludes a storage controller coupled to a plurality of hosts and aplurality of logical volumes, in accordance with certain embodiments;

FIG. 2 illustrates a block diagram of an exemplary embodiment in which alicensing application restricts enablement of a feature for a logicalvolume when the licensed capacity limit has been reached, in accordancewith certain embodiments;

FIG. 3 illustrates a block diagram that shows exemplary resource groupsgenerated from logical volumes, in accordance with certain embodiments;

FIG. 4 illustrates a block diagram that shows how enabling a feature ina resource group enables the feature in all logical volumes of theresource group, in accordance with certain embodiments;

FIG. 5 illustrates a first flowchart that shows how a licensingapplication enables or restricts enablement of a feature for a logicalvolume, in accordance with certain embodiments;

FIG. 6 illustrates a second flowchart that shows how a licensingapplication enables or restricts enablement of a feature for a resourcegroup, in accordance with certain embodiments;

FIG. 7 illustrates a block diagram that shows how the storage controllersends an interrupt to a host, in accordance with certain embodiments;

FIG. 8 illustrates a third flowchart, in accordance with certainembodiments; and

FIG. 9 illustrates a block diagram of a computational system that showscertain elements that may be included in the storage controller of FIG.1, in accordance with certain embodiments.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanyingdrawings which form a part hereof and which illustrate severalembodiments. It is understood that other embodiments may be utilized andstructural and operational changes may be made.

The enablement or disablement of features may be performed with respectto storage products. For example, a product may be configured such thata function may be enabled or disabled for an exemplary Count-Key-Data(CKD) storage. The level of granularity for enablement of features insuch cases is at the CKD storage level. CKD is a disk data organizationmodel in which the disk is assumed to consist of a fixed number oftracks, each having a maximum data capacity.

In certain environments, the above level of granularity at the CKDstorage level may be inadequate. Certain users may prefer to use aselected function on specific logical volumes, as opposed to all CKDvolumes, It may be noted that each CKD volume may be logically mappedinto a plurality of logical volumes.

Certain embodiments provides a mechanism to enable a feature at thegranularity of a logical volume while at the same time ensuring that thetotal amount of storage that may be used for the enabled feature doesnot exceed a licensed storage capacity corresponding to the feature.

In certain embodiments, the mechanism for determining whether a licensedstorage capacity limit is violated (i.e., exceeded) is implemented bydetermining the sum of the storage capacities of all storage volumesthat are currently enabled, adding to this sum the storage capacities ofany storage volumes that are requested to be enabled, and comparing thissum to a licensed storage capacity limit in a licensing key such thatthe licensed storage capacity limit is not violated if the sum of thestorage volume capacities of the currently enabled and the to be enabledstorage volumes is less than or equal to the licensed storage capacitylimit.

EXEMPLARY EMBODIMENTS

FIG. 1 illustrates a block diagram of a computing environment 100 thatincludes a storage controller 102 coupled to a plurality of hosts 104 a. . . 104 m and a plurality of logical volumes 106 a . . . 106 n, inaccordance with certain embodiments. In certain embodiments, the storagecontroller 102 and the hosts 104 a . . . 104 m may comprise any suitablecomputational device, including those presently known in the art, suchas, a personal computer, a workstation, a server, a mainframe, a handheld computer, a palm top computer, a telephony device, a networkappliance, a blade computer, a storage server, etc. The logical volumes106 a . . . 106 n may comprise logical representations corresponding toone or more physical volumes maintained in storage devices coupled tothe storage controller 102.

A licensing application 108 may execute within the storage controller102. The licensing application 108 maintains data structures to indicatethe licensed capacity limits 110 a . . . 110 p and the correspondingused capacity limits 112 a . . . 112 p for a plurality of features.

The licensing application 108 also controls logical volume attributes114 a . . . 114 n associated with the logical volumes 106 a . . . 106 n.Each logical volume attribute associated with a logical volume has foreach of a plurality of features an indicator that indicates enablementor disablement of the feature, and an indicator that indicates thestorage capacity of the logical volume. For example, logical volumeattribute 114 a for logical volume 106 a has enablement/disablementindicators 118 a . . . 118 p corresponding to features 116 a . . . 116p, and the logical volume capacity indicator 120. Similarly, logicalvolume attribute 114 n for logical volume 106 n hasenablement/disablement indicators 124 a . . . 124 p corresponding tofeatures 122 a . . . 122 p, and the logical volume capacity indicator126.

In certain embodiments, the licensing application 108 may enable afeature for a logical volume by setting the enablement/disablementindicator corresponding to the feature to an enabled state. For example,the licensing application 108 may enable the feature 116 a for thelogical volume 106 a by setting the enablement/disablement indicator 118a to an enabled state. While enabling a feature for the logical volume,the licensing application 108 ensures that the licensed capacity limitof the feature is not exceeded, wherein exemplary capacity limits offeatures are shown via reference numerals 110 a . . . 110 p.

FIG. 2 illustrates a block diagram of an exemplary embodiment 200 inwhich the licensing application 108 restricts enablement of a featurefor a logical volume when the licensed capacity limit for the featurehas been reached, in accordance with certain embodiments.

In the exemplary embodiment 200, three logical volumes A, B, C(indicated via reference numerals 202, 204, 206) and the correspondinglogical volume attributes 208, 210, 212 are shown. Feature X and FeatureY have been enabled (as shown via reference numerals 214, 216, 218, 220)for logical volume A 202, whereas feature X has been enabled (as shownvia reference numerals 222, 224) for logical volume B 204, wherein thelogical volume capacity 226 of logical volume A 202 is 2800 GB, andwherein the logical volume capacity 228 of logical volume B 204 is 1100GB.

Feature X is enabled for logical volume A 202 and logical volume B 204,wherein the capacity of logical volume A is 2800 GB and the capacity oflogical volume B is 1100 GB. Therefore, the used capacity for feature X(shown via reference numeral 230) is the sum of 2800 GB and 1100 GBwhich is 3900 GB. Feature Y is enabled for logical volume A 202, whereinthe capacity 226 of logical volume A is 2800 GB. Therefore, the usedcapacity for feature Y (shown via reference numeral 232) is 2800 GB.

FIG. 2 also indicates that the licensed capacity limit of feature X 234is 4000 GB and the licensed capacity limit of feature Y 236 is 3000 GB.In such a situation, if an enablement of feature X 238 is desired forlogical volume C 206 that has a logical volume capacity 240 of 2000 GB,then the licensing application 108 restricts (shown via referencenumeral 242) the enablement of feature X for logical volume C becauseenabling feature X for logical volume C 206 would cause the usedcapacity for feature X to be the sum of the already used 3900 GB (shownvia reference numeral 230) and the 2000 GB capacity (shown via referencenumeral 240) of logical volume C 206, and this sum of 5900 GB wouldexceed the 4000 GB licensed capacity limit of feature X (shown viareference numeral 234).

Therefore, FIG. 2 illustrates certain embodiments in which a feature isnot enabled for a logical volume, if enabling the feature for thelogical volume would cause the licensed capacity limit of the feature tobe exceeded.

FIG. 3 illustrates a block diagram 300 that shows exemplary resourcegroups 302, 304 generated from a plurality of logical volumes 306, 308,310, 312, 314, in accordance with certain embodiments. Each exemplaryresource group has one or more logical volumes.

In FIG. 3, an exemplary licensed capacity limit 316 for a feature andthe used capacity 318 for the feature are also shown. When the licensingapplication 108 enables a feature for an exemplary resource group, thenthe feature is enabled for all logical volumes that belong to theresource group. For example, enabling a feature for exemplary resourcegroup 304 enables the feature for logical volumes 310, 312, 314, and theused capacity 318 of the feature increases by the sum of capacities ofthe logical volumes 310, 312, and 314. In certain embodiments, themechanism to associate an exemplary logical volume with a resource groupis to add a “resource group” attribute to each exemplary logical volumesuch that all logical volumes which specify “resource group”=N areassociated with resource group N.

FIG. 4 illustrates a block diagram 400 that shows how enabling a featurein a resource group 402 enables the corresponding feature in logicalvolumes 404 a . . . 404 q of the resource group 402, in accordance withcertain embodiments.

In FIG. 4, the licensing application 108 (shown in FIG. 1) maintainsresource group attributes 406 corresponding to the resource group 402.Corresponding to a plurality of features 408 a . . . 408 n,enablement/disablement indicators 410 a . . . 410 n are maintained inthe resource group attributes 406. The licensing application 108 alsomaintains for the logical volumes 404 a . . . 404 q of the resourcegroup 402 corresponding logical volume attributes 414 a . . . 414 q.

In certain exemplary embodiments, if a customer or a user enables anexemplary feature A 408 a in the resource group attributes 406, then thelicensing application 108 enables feature A 416 a . . . 416 q for allthe logical volumes 404 a . . . 404 q.

It should be noted that in FIG. 4, although enablement/disablementsindicators have been shown associated with features in the logicalvolume attributes 114 a . . . 114 q, in the embodiments illustrated inFIG. 4 the enablement attributes for features are provided by theattributes 406 of the resource group 402 and not by the attributes 414 a. . . 414 q of the logical volumes 404 a . . . 404 q. In the embodimentillustrated by FIG. 4, the individual enablement/disablement indicationon each logical volume for a given feature would only be modifiedthrough the setting of the resource group's 402 associatedenablement/disablement indicators 410 a . . . 410 n for a given feature.

The embodiments shown in FIG. 4 prevent the logical volume attributesfrom being modified independently. The logical volume's 404 a . . . 404q enablement/disablement indicators for a given feature must all havethe same value which is equal to the resource group's 402 value for aselected feature's 408 a . . . 408 n enablement/disablement indicator410 a . . . 412 n.

In certain alternative embodiments, when logical volumes are placed inresource groups, individual enablement/disablement indicators are notlonger maintained in logical volume attributes of logical volumes .

FIG. 5 illustrates a first flowchart 500 that shows how the licensingapplication 108 enables or restricts enablement of a feature for alogical volume, in accordance with certain embodiments. The operationsshown in the first flowchart 500 may be performed by executing thelicensing application 108 within the storage controller 102.

Controls starts at block 502 in which a preinitialization of licensedcapacity limits 110 a . . . 110 p for features are performed. Thepreinitialization of features may be based on licensing terms purchasedby a customer from a vendor of a software or a hardware product that hasa plurality of features, wherein selected features from the plurality offeatures may be enabled based on the licensing terms, and wherein thelicensing terms also include capacity limits for each feature. Thepreinitialization may be performed by the licensing application 108based on interactions with the customer or a user via a graphical userinterface or via a command line interface.

Control proceeds to block 504, and the licensing application 108receives a request to enable a feature for a logical volume. Thelicensing application 108 determines (at block 506) whether enabling thefeature for the logical volume causes the licensed capacity limit 110 a. . . 110 p for the feature to be exceeded. If so, the licensingapplication 108 restricts (at block 508) enablement of the feature forthe logical volume.

If enabling the feature for the logical volume causes the licensedcapacity limit 110 a . . . 110 p for the feature not to be exceeded,then the licensing application 108 enables (at block 510) the featurefor the logical volume and updates the capacity used indicator 112 a . .. 112 p for the feature to reflect the addition of the capacity of thelogical volume.

Therefore, FIG. 5 illustrates certain embodiments in which the licensingapplication 108 enables or restricts enablement of a feature for alogical volume based on the licensed capacity limit for the feature.

FIG. 6 illustrates a second flowchart 600 that shows how a licensingapplication 108 enables or restricts enablement of a feature for aresource group (such as, exemplary resource group 402), in accordancewith certain embodiments. The operations shown in the second flowchart600 may be performed by executing the licensing application 108 withinthe storage controller 102.

Control starts as block 602, in which a preinitialization of licensedcapacity limit 110 a . . . 110 p for features takes place. The licensingapplication 108 receives (at block 604) a request to enable a featurefor a resource group 402.

The licensing application 108 determines (at block 606) whether enablingthe feature in all logical volumes included in the resource group willcause the licensed capacity limit for the feature to be exceeded. If so,the licensing application 108 restricts (at block 608) enablement of thefeature for the resource group 402.

If the licensing application 108 determines that enabling the feature inall logical volumes included in the resource group 402 will not causethe licensed capacity limit for the feature to be exceeded, then thelicensing application 108 enables (at block 610) the feature for alllogical volumes included in the resource group and updates the capacityused indicator 112 a . . . 112 p for the feature to add the totalcapacity of all the logical volumes included in the resource group 402.

Therefore, FIG. 6 illustrates certain embodiments in which the licensingapplication 108 enables or restricts enablement of a feature for aresource group having a plurality of logical volumes based on thelicensed capacity limit for the feature.

FIG. 7 illustrates a block diagram 700 that shows how the storagecontroller 102 sends an interrupt to an exemplary host 106 a, inaccordance with certain embodiments. The operations shown in the blockdiagram 700 may be performed by executing the licensing application 108within the storage controller 102.

When the status of a logical volume 106 a . . . 106 n changes, i.e., afeature is enabled or disabled for a logical volume, the change instatus of the logical volume should be conveyed by the storagecontroller 102 to the hosts 104 a . . . 104 m, such that the feature canbe used or not used by the host with respect to the logical volume.Since there may be numerous changes to the status of numerous logicalvolumes (e.g., there may be 64 K logical volumes in certainembodiments), if an interrupt is sent for every status change in eachlogical volume, then the hosts 104 a . . . 104 m may be overburdened byreceiving numerous interrupts and significant processing power of thehosts may be used in servicing the numerous interrupts.

In certain embodiments, the storage controller 102 sends (shown viareference numeral 702) a single interrupt to each exemplary host (suchas, exemplary host 104 a) to indicate the changed status of logicalvolumes of a group of sequentially numbered logical volumes that havebeen enabled/disabled for one or more features. The single interruptconveys the status of a group of logical volumes. For example, if thereare N enablement/disablement indicators for each logical volume, and 256sequentially numbered logical volumes are grouped for the purposes ofsending interrupts, then a (256×N) array may convey the status of allthe N features for each of the 256 logical volumes via a singleinterrupt.

Therefore, FIG. 7 illustrates certain embodiments in which a singlenotification is presented via a single interrupt for all the logicalvolumes with a range of 256 addresses to reduce the number ofnotifications required. The notification via the single interruptindicates the enablement/disablement status of all features of a groupof logical volumes to an exemplary host. FIG. 7 illustrates exemplaryembodiments, in which in response to an enablement or disablement of oneor more selected features for one or more logical volumes of a group ofsequentially numbered logical volumes, a single interrupt is sent fromthe storage controller 101 to each host of a plurality of hosts that arecoupled to the storage controller 102, wherein the single interrupt isindicative of changes in the one or more selected features for alllogical volumes of the group of sequentially numbered logical volumes.

FIG. 8 illustrates a third flowchart 800, in accordance with certainembodiments. The operations shown in the third flowchart 800 may beperformed by executing the licensing application 108 within the storagecontroller 102.

Control starts at block 802, in which a licensing application 108implemented in a computational device 102 (e.g., the storage controller102) receives a request to enable a feature for a logical volume of aplurality of logical volumes 106 a . . . 106 n controlled by thecomputational device 102, wherein each feature of a plurality offeatures is configurable to be enabled or disabled for one or morelogical volumes of the plurality of logical volumes.

The licensing application 108 determines (at block 804) whether enablingthe feature for the logical volume causes a licensed capacity limit(e.g., 110 a) for the feature to be exceeded, If so (i.e., the “Yes”branch from block 804), the licensing application 108 avoids (at block806) enabling the feature for the logical volume,

In response to determining (at block 804) that enabling the feature forthe logical volume causes the licensed capacity limit for the featurenot to be exceeded (i.e., the “No” branch from block 804), the licensingapplication 108 enables (at block 808) the feature for the logicalvolume.

Therefore, FIG. 8 illustrates certain embodiments in which a licensingapplication enables or disables features at the granularity of logicalvolumes based on the licensed capacity corresponding to the feature. Itshould be noted that certain embodiments shown in FIG. 8 are applicableto the situation in which there are no resource groups. However, incertain embodiments a mechanism is provided to allow theenablement/disablement control to be specified for a group of volumesvia the usage of a resource group, and as a result the need to controlthe enablement/disablement on each volume as a separate request isavoided.

ADDITIONAL EMBODIMENT DETAILS

The described operations may be implemented as a method, apparatus orcomputer program product using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. Accordingly, aspects of the embodiments may take the form of anentirely hardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,aspects of the embodiments may take the form of a computer programproduct embodied in one or more computer readable medium(s) havingcomputer readable program code embodied there.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java*, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

FIG. 9 illustrates a block diagram that shows certain elements that maybe included in the system 900 in accordance with certain embodiments.The system 900 may comprise the storage controller 102 and may include acircuitry 902 that may in certain embodiments include at least aprocessor 904. The system 900 may also include a memory 906 (e.g., avolatile memory device), and storage 908. The storage 908 may include anon-volatile memory device (e.g., EEPROM, ROM, PROM, RAM, DRAM, SRAM,flash, firmware, programmable logic, etc.), magnetic disk drive, opticaldisk drive, tape drive, etc. The storage 908 may comprise an internalstorage device, an attached storage device and/or a network accessiblestorage device. The system 900 may include a program logic 910 includingcode 912 that may be loaded into the memory 906 and executed by theprocessor 904 or circuitry 902. In certain embodiments, the programlogic 910 including code 912 may be stored in the storage 908. Incertain other embodiments, the program logic 910 may be implemented inthe circuitry 902. Therefore, while FIG. 9 shows the program logic 910separately from the other elements, the program logic 910 may beimplemented in the memory 906 and/or the circuitry 902.

Certain embodiments may be directed to a method for deploying computinginstruction by a person or automated processing integratingcomputer-readable code into a computing system, wherein the code incombination with the computing system is enabled to perform theoperations of the described embodiments.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

Further, although process steps, method steps, algorithms or the likemay be described in a sequential order, such processes, methods andalgorithms may be configured to work in alternate orders. In otherwords, any sequence or order of steps that may be described does notnecessarily indicate a requirement that the steps be performed in thatorder. The steps of processes described herein may be performed in anyorder practical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

At least certain operations that may have been illustrated in thefigures show certain events occurring in a certain order. In alternativeembodiments, certain operations may be performed in a different order,modified or removed. Moreover, steps may be added to the above describedlogic and still conform to the described embodiments. Further,operations described herein may occur sequentially or certain operationsmay be processed in parallel. Yet further, operations may be performedby a single processing unit or by distributed processing units.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims hereinafter appended.

* Java is a trademark or registered trademark of Sun Microsystems, Inc.

1-20. (canceled)
 21. A method comprising: receiving, in a computationaldevice, a request to enable a feature for a logical volume of aplurality of logical volumes controlled by the computational device,wherein each feature of a plurality of features is configurable to beenabled or disabled for one or more logical volumes of the plurality oflogical volumes; and in response to an enablement or disablement of oneor more selected features for one or more logical volumes of a group ofsequentially numbered logical volumes, sending a single interrupt fromthe computational device to each host of a plurality of hosts that arecoupled to the computational device, wherein the single interrupt isindicative of changes in the one or more selected features for alllogical volumes of the group of sequentially numbered logical volumes.22. The method of claim 21, the method further comprising: determiningwhether enabling the feature for the logical volume causes a licensedcapacity limit for the feature to be exceeded.
 23. The method of claim22, the method further comprising: avoiding enabling the feature for thelogical volume, in response to determining that enabling the feature forthe logical volume causes the licensed capacity limit for the feature tobe exceeded.
 24. The method of claim 21, wherein the computationaldevice is a storage controller, wherein the plurality of logical volumesare generated from physical volumes of a plurality of storage devicescoupled to the storage controller.
 25. The method of claim 24, whereinselected logical volumes of the plurality of logical volumes are groupedinto a resource group, the method further comprising: in response to arequest for enablement of a selected feature for the resource group,determining whether enabling the selected feature for all the selectedlogical volumes of the resource group causes a licensed capacity limitfor the selected feature to be exceeded.
 26. A system, comprising: amemory; and a processor coupled to the memory, wherein the processorperforms operations, the operations comprising: receiving a request toenable a feature for a logical volume of a plurality of logical volumes,wherein each feature of a plurality of features is configurable to beenabled or disabled for one or more logical volumes of the plurality oflogical volumes; and in response to an enablement or disablement of oneor more selected features for one or more logical volumes of a group ofsequentially numbered logical volumes, sending a single interrupt fromthe computational device to each host of a plurality of hosts that arecoupled to the computational device, wherein the single interrupt isindicative of changes in the one or more selected features for alllogical volumes of the group of sequentially numbered logical volumes.27. The system of claim 26, the operations further comprising:determining whether enabling the feature for the logical volume causes alicensed capacity limit for the feature to be exceeded.
 28. The systemof claim 27, the operations further comprising: avoiding enabling thefeature for the logical volume, in response to determining that enablingthe feature for the logical volume causes the licensed capacity limitfor the feature to be exceeded.
 29. The system of claim 26, wherein thesystem is a storage controller, wherein the plurality of logical volumesare generated from physical volumes of a plurality of storage devicescoupled to the storage controller.
 30. The system of claim 29, whereinselected logical volumes of the plurality of logical volumes are groupedinto a resource group, the operations further comprising: in response toa request for enablement of a selected feature for the resource group,determining whether enabling the selected feature for all the selectedlogical volumes of the resource group causes a licensed capacity limitfor the selected feature to be exceeded.
 31. A computer program product,the computer program product comprising: a computer readable storagemedium having computer readable program code embodied therewith, thecomputer readable program code configured to perform operations, theoperations comprising: receiving, in a computational device, a requestto enable a feature for a logical volume of a plurality of logicalvolumes controlled by the computational device, wherein each feature ofa plurality of features is configurable to be enabled or disabled forone or more logical volumes of the plurality of logical volumes; and inresponse to an enablement or disablement of one or more selectedfeatures for one or more logical volumes of a group of sequentiallynumbered logical volumes, sending a single interrupt from thecomputational device to each host of a plurality of hosts that arecoupled to the computational device, wherein the single interrupt isindicative of changes in the one or more selected features for alllogical volumes of the group of sequentially numbered logical volumes.32. The computer program product of claim 31, the operations furthercomprising: determining whether enabling the feature for the logicalvolume causes a licensed capacity limit for the feature to be exceeded.33. The computer program product of claim 32, the operations furthercomprising: avoiding enabling the feature for the logical volume, inresponse to determining that enabling the feature for the logical volumecauses the licensed capacity limit for the feature to be exceeded. 34.The computer program product of claim 31, wherein the computationaldevice is a storage controller, wherein the plurality of logical volumesare generated from physical volumes of a plurality of storage devicescoupled to the storage controller.
 35. The computer program product ofclaim 34, wherein selected logical volumes of the plurality of logicalvolumes are grouped into a resource group, the operations furthercomprising: in response to a request for enablement of a selectedfeature for the resource group, determining whether enabling theselected feature for all the selected logical volumes of the resourcegroup causes a licensed capacity limit for the selected feature to beexceeded.